Skip to content

Add entry logger scanner stats#2886

Closed
wuzhanpeng wants to merge 1 commit intoapache:masterfrom
wuzhanpeng:feature_add_entry_logger_scanner_stats
Closed

Add entry logger scanner stats#2886
wuzhanpeng wants to merge 1 commit intoapache:masterfrom
wuzhanpeng:feature_add_entry_logger_scanner_stats

Conversation

@wuzhanpeng
Copy link

Descriptions of the changes in this PR:

Motivation

In our practice, when the throughput becomes larger, the trigger frequency of compaction will also increase, so that the scanning of entry log will also become frequent. It is well known that frequent read operations in HDD are a common cause of disk performance degradation, but we currently have no relevant monitoring information on this. Therefore, this pr provides a convenient way to provide additional monitoring of log scanning.

Changes

Add two counters for log scanning monitoring.

@wuzhanpeng
Copy link
Author

rerun failure checks

3 similar comments
@wuzhanpeng
Copy link
Author

rerun failure checks

@wuzhanpeng
Copy link
Author

rerun failure checks

@wuzhanpeng
Copy link
Author

rerun failure checks

@wuzhanpeng
Copy link
Author

@zymap Would you mind to help review it?

@hangc0276
Copy link
Contributor

@wuzhanpeng Thanks for your contribution, would you please rebase the master? thanks.

Copy link
Contributor

@hangc0276 hangc0276 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The scannedByte is not the real bytes read from disks because it uses BufferedReadChannel to do prefetch, and the OS PageCache also has prefetch. Please refer to #3192

}
data.capacity(entrySize);
int rc = readFromLogChannel(entryLogId, bc, data, pos);
entryLogCounter.numOfScannedBytes.add(data.writableBytes());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

data.readableBytes()?

@zymap
Copy link
Member

zymap commented Jul 29, 2022

@wuzhanpeng Do you want to continue to work on this? If not, I will remove the release label

@hangc0276 hangc0276 modified the milestones: 4.16.0, 4.17.0 Jul 29, 2022
@zymap
Copy link
Member

zymap commented Aug 1, 2022

Move it to the next release since this PR is inactive.

@StevenLuMT
Copy link
Member

fix old workflow,please see #3455 for detail

@hezhangjian
Copy link
Member

closed by inactive, feel free to reopen it if you still want to working on this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants